CI: rename GCP subnets used for integration specs#564
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughThis change updates GCP infrastructure naming in pipeline configuration files. The Suggested reviewers
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Renames the GCP subnets used by the CI integration/bats pipelines to a new stemcell-builder-integration-* naming scheme, and updates the subnet index used to derive CIDRs/IPs.
Changes:
- Update
stemcell_details.subnet_intfrom"3"to"22"(used for IP/CIDR derivation). - Rename
GCP_SUBNET_NAME/VARS_SUBNETWORK_DEFAULTvalues frombosh-integration-*tostemcell-builder-integration-*(including ipv6 variant).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| ci/pipelines/vars.yml | Updates the subnet index (subnet_int) used across GCP integration jobs. |
| ci/pipelines/builder.yml | Renames the GCP subnet names referenced by integration and BATs jobs (ipv4 + ipv6). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Pipeline already reconfigured.